The latest incarnation of Barry Kauler's Quirky based on Debian Trusty Tahr
Identifier Puppy_Linux_Quirky_TahrAddeddate 2014-01-29 22:30:53Mediatype softwareCreator Barry KaulerPublicdate 2014-01-29 22:31:00Filesxml Tue Jan 27 20:24:29 UTC 2015
Quirky Tahr builds on the same ideas, except is constructed with binary DEB packages from the Ubuntu Trusty Tahr repository.
This offers the enormous advantage of compatibility with the large Ubuntu repository, and the Quirky Package Manager can download any package from it.
Yet, this is a quirky Linux, quite unique. Instead of Trusty Tahr, you have Quirky Tahr, and the difference has to be experienced!
Quirky Tahr is built with the same "Quirky build system", with the same infrastructure and basic ideas, with some differences.
Quirky is a fork of Puppy Linux, focused for "full installation" only, as opposed to Puppy's multiple modes of installation. Having this focus, Quirky is optimised to run as a full installation in the simplest possible manner, that is, extreme ease-of-use, with tools for upgrading and recovery that are aimed to prevent your installation from ever becoming broken or compromised.
Where Quirky Tahr differs from Quirky is use of the Ubuntu Trusty Tahr binary DEB packages when putting it together. This does not make Quirky Tahr a clone of Ubuntu -- please, never think that! -- it is just that by using the Ubuntu packages, binary compatibility is achieved with the Ubuntu Trust Tahr package repository, and the Quirky Package Manager is able to install packages from that repo.
It also means that some of the "retro" features of Quirky are gone. Quirky was built with packages compiled from source in T2, with minimal dependencies, and some rather odd choices, such as use of GTK 2.20.1 rather than 2.24.x (latest in the 2.x series). Quirky is very small, a build with light-weight browser weighs in at about 100MB (download file), whereas Quirky Tahr is around 150MB.
That's the difference mostly, with Quirky Tahr, built from Ubuntu DEBs, the packages have many more dependencies, and of course they also must be included in the build. If you want to know just what Ubuntu packages have been used in this build, see here: